pp108 : Java Archive Definition Interface

Java Archive Definition Interface
This topic provides information on the fields that you fill while creating a Java Archive Definition.

The interface contains two tabs - one to enter generic information and the other one to store any dependency to other sources.

Tab Field Name Description User Action
General Name Name of the Java Archive Definition file Provide a name
Description Description of the Java Archive Definition Provide a brief description
JAR File Name Name of the JAR File that will be created, which will contain the build output of all the Java sources (.class files) Provide a name for the JAR file
JAR-Content Folder The folder from which Java source files will be included Next to the field, click to browse and select the project/folder that contains the Java sources.
Note: The JAR will contain the build output of the Java sources - the .class files. As the documents will be published according to the publish logic of Java Archive Definition, the JAR will also include all the folders and documents (including other Process Platform documents) that exist in this folder.
By default, the .JAR file will be stored under <Process Platform install dir>/<instance name>/<qualified name of the root folder> at runtime.
If the .JAR file was created on WS-AppServer content, it is stored at <Process_Platform_Installation_Directory>\<instance name>\bsf\runtime\<organization>.
To exclude files that must be outside the scope of JAR, set the QN on a folder.
Dependencies - Include JAR files or Java Archive Sources which share dependency with the Java Archive Source that you are going to create. This information is optional.
Click to select a relevant type of dependency. The Java Archive Dependency Wizard appears. Select one of the options given in the following rows.
Java Archive Source Adds an existing Java Archive Source available in the workspace as a dependent file Select the option, click Next to browse the solution and select the relevant Java Archive Source, and click Finish to fill the dependency.
This will create a package dependency on the providing application package.
Internal Archive Source Adds an existing Java Archive (JAR) available in the workspace as a dependent file Select the option, click Next to browse the solution and select the relevant Java Archive, and click Finish to fill the dependency.
This will create a package dependency on the providing application package.
External Java Archive Adds an external JAR to the project and creates the dependency

Select the option and click Next. On the next page, provide the dependency details. You can provide:

  • only the relative or absolute file system path of the Java archive in the Enter the path to the external JAR field and leave the name of the providing application package in the Enter the application package name field empty.
    This will not create any new package dependencies and can be selected when a Java Archive is used in applications that are deployed on the development/production environment outside Cordys.
  • both the relative or absolute file system path of the Java archive in the Enter the path to the external JAR field and the name of the providing application package in the Enter the application package name field.
    This will create a package dependency on the providing application package and can be selected when a Java Archive is used from a third party Process Platform application. Note that the name of the providing application package may be different from the file name of the providing package. Refer to Setting Properties of an Application Package for more information.